Configuration, compilation and getting started with the software:
3.4 Q - Making changes to the Salvo source code and the "buildit" script
A - When a change is made to the Salvo code, in the salvo directory, the "buildit" script needs
to be run so the Salvo library can be re-built.
This is a simple process where all you need to do is:
From the GS3Stack/source directory:
$cd salvo
$./buildit
This procedure needs to be run whenever you modify the Salvo source code and, most
importantly, the "salvocfg.h" file in the GS3Stack/source directory.
3.5 Q - Adding user modules
A - To add your own modules, follow these steps:
1. Create your .c and .h source files.
2. Add your .h files in the Makefile "include files section"
3. Add your .c files in the Makefile "c source files section"
4. Add your initialization routines in the main.c "User Module Initialization" section.
5. If you are using Salvo routines, make sure that you add your task and message
queue initialization code in the mxinit.c file.
Look for the "User Task Initialization" and "User Message Initialization" sections.
6. If you are not using Salvo and still want to multitask, put your multitask
function calls in the main.c multitasking loop.
That is all you need.
If you will be using any of the system services, provided by the hardware, make
sure you use the proper software interface.
For example, serial port I/O should be done via the USARTPutChar or
USARTPutString functions.
If you need I2C bus services, you should use the appropriate message queue to
communicate with the I2C bus master handler.
Please see the appropriate sections below for more information.
